TeX 1995 July

home *** CD-ROM | disk | FTP | other *** search

/ TeX 1995 July / TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO / systems / mac / euro-oztex / EOT2.1#2.sea.bin / HyperBibTeX / HyperBibTeX Help / cards.xml < prev next >

Wrap

Text File | 1993-10-01 | 88KB | 1,058 lines

card_11621.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>11621</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Using the Message Box</text> </content> <content> <layer>background</layer> <id>2</id> <text>he HyperCard Message Box can be used to directly execute HyperTalk commands not otherwise available via HyperBibTeX commands. (But note that HyperCard Player does not permit commands to be run from the Message Box.) The Message Box is accessed by pressing ΓîÿM or choosing the Message command on the Go menu. Since HyperBibTeX sets the userlevel to 3, not all commands will be available. Use caution in directly running commands in this way; it may be possible to damage the stack or the data contained in it.Here are examples of some useful HyperTalk commands that can be run from the Message Box: go card number go last go first show cards show marked cards find "string " <a href="#" class="group">mark card</a>s where expression un<a href="#" class="group">mark card</a>s where expression print number cards</text> </content> <name>Using the Message Box</name> <script></script> </card> card_7814.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>7814</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Function Keys</text> </content> <content> <layer>background</layer> <id>2</id> <text>he function keys and other grey keys on the extended keyboard (except the keypad) can be customized by the user by editing the functionKey and keyDown handlers in the stack script. Here are the defaults:F5 <a href="#" class="group">Find</a>F6 NextF7 <a href="#" class="group">Mard Card</a>sF8 Un<a href="#" class="group">mark Card</a>sF9 <a href="#" class="group">Index</a> WindowF10 <a href="#" class="group">Sort</a>F11 <a href="#" class="group">Check Keys</a>F12 <a href="#" class="group">Find Duplicates</a>F13 <a href="#" class="group">Verify Field</a>F14 Edit ListF15 Set <a href="#" class="group">Preferences</a>Home Go FirstEnd Go Last (data card)PageUp Go PrevPageDn Go NextDel (disabled)</text> </content> <name>Function Keys</name> <script></script> </card> card_8572.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>8572</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Command Keys</text> </content> <content> <layer>background</layer> <id>2</id> <text>he command key aliases for menu commands can be customized by the user by editing the commandkeyDown handler in the stack script. Here are the defaults:ΓîÿN New Card of current entry typeΓîÿDelete Delete CardΓîÿF <a href="#" class="group">Find</a>ΓîÿG Find NextΓîÿJ Navigator Palette (see setupMenus handler)ΓîÿK Mark/Un<a href="#" class="group">mark Card</a>Other command keys have their usual HyperCard values.</text> </content> <name>Command Keys</name> <script></script> </card> card_8907.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>8907</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Printing Cards</text> </content> <content> <layer>background</layer> <id>2</id> <text>se the command Print Card on the File menu to print the current card. Use the command Print Stack... on the File menu to print all the cards or just the <a href="#" class="group">marked card</a>s.</text> </content> <name>Printing Cards</name> <script></script> </card> card_12589.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>12589</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>2</id> <text>f you have a bibliography stack created with an older version of HyperBibTeX, you should convert it to the current version. Do the following.IMPORTANT: If you are using HyperBibTeX version 0.9.5 (that is, 0.9.5d, 0.9.5e, or 0.9.5f) you must first fix a bug in the Export command (it drops certain non-BibTeX fields, namely ISBN, Location, and Annote). The current release of HyperBibTeX (version 0.9.8 or higher) includes a special stack called ΓÇ£Patch HyperBibTeX 0.9.5ΓÇ¥which patches the stack ΓÇ£HyperBibTeX UtilsΓÇ¥. Open the patching stack and follow the instructions. If you don't do this you may lose data ! 1. After patching the Utils stack, open your bibliography stack (say, MyBiblioStack) and go to the <a href="#" class="group">Preferences</a> card (choose "Preferences" on the Commands menu).2. Ensure that the option "Expand <a href="#" class="group">abbreviations</a>" is *NOT* checked. Choose either quotes or braces as field delimiters.3. Type a file name into the box "BibTeX file name" (optional).4. Leave the Preferences card (return to the main part of the stack).5. Choose "<a href="#" class="group">Export</a>..." on the Commands menu. 5a. <a href="#" class="group">Sort</a> the stack if desired, otherwise click "Skip". 5b. Select ALL cards. 5c. Select ALL non-BibTeX fields. 5d. Select a file name and click "Save".6. Close the stack (MyBiblioStack).7. Make a copy of the blank stack supplied with the current release of HyperBibTeX, rename it (MyNewBiblioStack), and open it.8. Ensure that any <a href="#" class="group">user-defined fields</a> you have used in the .BIB file are declared in the box "User-defined field names" (these should be listed in the old stack).9. Choose whether or not to convert accented characters.10. Choose "<a href="#" class="group">Import</a>..." on the Commands menu and select the .BIB file you just exported.11. If you are asked "Import abbreviation strings?", click "No".12. When the importing is finished, all that remains is rebuild the <a href="#" class="group">authority lists</a>. To do this, open the old stack in a new window and copy and paste each authority list from the old stack to the new stack (there are four lists). (Alternatively, use the Verify Field command to rebuild the lists.)12. Be sure to replace old copies of the stacks "HyperBibTex Utils" and "HyperBibTeX Help" with new ones. There should be only one copy of each of these stacks on your system.</text> </content> <content> <layer>background</layer> <id>1</id> <text>Upgrading to a new version of HyperBibTeX</text> </content> <name>Upgrading to a new version o</name> <script></script> </card> card_9469.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>9469</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>2</id> <text>OTE: HyperBibTeX version 0.9.5 had a <a href="#" class="group">bug</a> that caused certain <a href="#" class="group">user-defined fields</a> to be dropped when importing. Please <a href="#" class="group">upgrade</a> to a newer version of HyperBibTeX.Disclaimer: I have tested the importing function with BibTeX files from various sources, but there is no guarantee that it will correctly handle all possible BibTeX files. If necessary, edit your .BIB files in accord with the following limitations of HyperBibTeX's importing facility:ΓÇó HyperBibTeX will handle either quotes or braces as field delimiters but recognizes only braces as the outermost delimiters of an entry (BibTeX permits parentheses as outermost delimiters).ΓÇó HyperBibTeX does NOT support concatenated abbreviations (introduced in BibTeX version 0.99b).ΓÇó If HyperBibTeX encounters an at-sign (@) used in a field of an entry, it will skip the rest of that entry (it assumes that an at-sign always signals the beginning of an entry). Look for e-mail addresses that use the @ character.Before importing entries from a BibTeX (.BIB) file, go to the <a href="#" class="group">Preferences</a> card (choose Preferences on the Commands menu) and set the following two options.First, if the .BIB file contains fields that are not standard BibTeX fields (other than extra fields that HyperBibTeX knows about such as Location, Keywords, and ISBN), you should list these <a href="#" class="group">user-defined</a> field names in the appropriate box; otherwise they will not be imported. Such fields will be placed in the special field accessed with the User Fields button.Second, if you want to use Macintosh <a href="#" class="group">accented characters</a> (such as ├⌐) in the stack, check the box "Convert accents" and be sure that the provided list of accented characters contains all the characters you need.To import entries from a BibTeX (.BIB) file, use the Import command on the Commands menu.If the BibTeX file contains <a href="#" class="group">abbreviation</a> strings, you will be asked if you want to import them. If all these abbreviations are already in your <a href="#" class="group">authority list</a>s, reply No. If you reply Yes, the abbreviations will be placed in the Authors list (since HyperBibTeX doesn't know the correct place to put them). Just cut and paste them into the proper lists.After importing entries, you can automatically build <a href="#" class="group">authority list</a>s by using the <a href="#" class="group">Verify Field</a> command with the option not to confirm adding new items.The contents of a Key field (not the same thing as the entry key used in the \cite command) will be placed after the entry key separated by an exclamation point (see the Help card <a href="#" class="group">Entry Key versus Key Field</a>).If an InBook, InCollection, or InProceedings entry includes fields for the Book or Proceedings that contains the excerpt, these fields are placed in User Fields of the In... card.</text> </content> <content> <layer>background</layer> <id>1</id> <text>Importing</text> </content> <name>Importing</name> <script></script> </card> card_7432.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>7432</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Exporting</text> </content> <content> <layer>background</layer> <id>2</id> <text>OTE: HyperBibTeX version 0.9.5 had a <a href="#" class="group">bug</a> that caused the ISBN, Location, and Annote fields to be dropped when exporting. Please <a href="#" class="group">upgrade</a> to a newer version of HyperBibTeX.Before importing entries from a BibTeX (.BIB) file, go to the <a href="#" class="group">Preferences</a> card (choose Preferences on the Commands menu) and set the following options. First, you can choose whether or not to expand <a href="#" class="group">abbreviation</a>s when exporting. If you don't expand abbreviations, HyperBibTeX will automatically also export all your abbreviations as BibTeX @STRING definitions.Second, you can choose what type of field delimiters to use in the exported .BIB file: either double quotes ("...") or braces ({...}). If your bibliography contains umlauted vowels such as \"{u}, then you should use braces. This choice has no effect when <a href="#" class="group">importing</a> a .BIB file.Third, you can choose to <a href="#" class="group">export</a> all InBook, InCollection, and InProceedings entries before all other entries. This is necessary only if these In* entries use the <a href="#" class="group">CrossRef</a> field.Fourth, you can choose to export a BookTitle field for Book and Proceedings entries. This may be necessary if you are using <a href="#" class="group">cross-reference</a>d entries in order to avoid BibTeX errors.Fifth, you can choose to convert Macintosh accented characters such as ├⌐ to TeX macros (such as {\'e}). (If you are using an eight-bit version of TeX that can handle accented characters, then you may not need to do this.) If your stack does not use accented characters, then uncheck the "Convert accents" box in order to speed up exporting.To export cards to a BibTeX (.BIB) file: (1) If you want to export only certain cards, use the <a href="#" class="group">Mark Card</a>s command on the Commands menu. (2) Do the Export command on the Commands menu. ΓÇó First you are asked to choose which cards to export (All or Selected). ΓÇó Next you are asked to choose which non-BibTeX fields to export: ISBN, Location, Keywords, Annote (strictly a BibTeX field but rarely used), and <a href="#" class="group">User Fields</a>. Note that <a href="#" class="group">User Fields</a> will automatically be exported for the <a href="#" class="group">entry types</a> InBook, InCollection, and InProceedings since they may contain valid BibTeX fields (see the Help card on <a href="#" class="group">Cross-references</a>). ΓÇó Last you are asked to choose the export file name (which uses the default name found on the <a href="#" class="group">Preferences</a> card).Note that if the Author field of a card is empty, HyperBibTeX will export a Key field which contains the part of the card key after the exclamation point (see the Help card <a href="#" class="group">Entry Key versus Key Field</a>).</text> </content> <name>Exporting</name> <script></script> </card> card_7391.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>7391</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Verifying Field Contents</text> </content> <content> <layer>background</layer> <id>2</id> <text>o verify that a field contains only data included in its <a href="#" class="group">authority list</a>, use the Verify Field command on the Utility menu. The command goes through the stack (starting with the current card) checking to see if the contents of the chosen field are in the authority list for that field. (Note that the status of the "Verify data entry" button on the <a href="#" class="group">Preferences</a> card is irrelevant to the operation of the Verify Field menu command.)When you run the Verify Field command, it first asks you to select a field (such as Author, Journal, Publisher, etc.); then it asks if you want to confirm each new item before adding it to the authority list. If you choose to confirm adding new items, each time it finds a field whose contents are not in the authority list, it puts up a dialog box and asks you whether or not you want to add it to the list. This procedure is recommended if you already have entries in the authority list and just want to check a field against the list. If you choose not to confirm new items, they will automatically be added to the appropriate list (except that you will be asked to define <a href="#" class="group">abbreviations</a>). This is the best way to build authority lists when you have built a new stack by <a href="#" class="group">import</a>ing entries from a BibTeX file and the authority lists are empty.</text> </content> <name>Verifying Field Contents</name> <script></script> </card> card_10487.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>10487</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Authority Lists</text> </content> <content> <layer>background</layer> <id>2</id> <text>yperBibTeX maintains four authority lists of bibliographic data. Three of the lists serve more than one field. The lists and the fields they serve are as follows:Author/EditorJournal/Series/TypePublisher/Organization/Institution/School/HowPublishedKeywordsNote: BibTeX uses the Type field to mean different things in different <a href="#" class="group">entry types</a>. In a TechReport entry, Type means the kind of report, while in an InBook or InCollection entry, Type means the kind of excerpt (e.g. chapter or selection).To manually edit an authority list, choose the Edit List command on the Commands menu. The list will be automatically cleaned up (extra white space removed) and sorted when you close the field. Use the arrow buttons to go from one list to another. When you are done, click on the return arrow.To automatically add the contents of a field to an authority list, use the <a href="#" class="group">Verify Field</a> command.</text> </content> <name>Authority Lists</name> <script></script> </card> card_6989.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>6989</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Finding Duplicate Cards</text> </content> <content> <layer>background</layer> <id>2</id> <text>o find possible duplicate cards in the stack: (1) <a href="#" class="group">Sort</a> the stack. (2) Go to the first card in the stack. (3) Do the Find Duplicates command on the Commands menu.The process will stop on when a card that is a possible duplicate with the next card is found. Resolve the problem and then do the Find Duplicates command again (which always starts with the current card).The Find Duplicates command always checks the entry key when trying to discover duplicates. If you <a href="#" class="group">sort</a> on a field other than the entry key, then it will use both the sort field and the entry key.</text> </content> <name>Finding Duplicate Cards</name> <script></script> </card> card_9479.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>9479</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Checking Keys</text> </content> <content> <layer>background</layer> <id>2</id> <text>he Check Keys command on the Utility menu does the following:ΓÇó it checks to see if the entry key is empty or if another card has the same key;ΓÇó for cards of the <a href="#" class="group">entry type</a> InBook, InCollection, or InProceedings, it checks to see if the CrossRef Key field is empty or if no card can be found with that key.The Check Keys command starts at the current card and goes through the stack to the end. When it finds an error, it presents a dialog box with two choices: Fix it or Continue. ΓÇó If you choose Fix it, the process halts at the card where the error was found. After you correct the error, do the Check Keys command again to restart checking from that point in the stack.ΓÇó If you choose Continue, the checking process will continue without giving you a chance to correct the error.</text> </content> <name>Checking Keys</name> <script></script> </card> card_6832.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>6832</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Marking and Unmarking Cards</text> </content> <content> <layer>background</layer> <id>2</id> <text>arked cards are used by the <a href="#" class="group">Index</a>, <a href="#" class="group">Export</a>, and Delete Marked Cards commands. See also the <a href="#" class="group">Navigation</a> help card.To mark or unmark a single card, click in the Marked box. Also, pressing ΓîÿK will mark or unmark a card.To mark or unmark more than a single card at a time, use the commands Mark Cards and Unmark Cards on the Commands menu. You will see a dialog box with the buttons Cancel, Selected, and All. ΓÇóThe All button will mark/unmark all cards in the stack. ΓÇóThe Selected button will first execute the <a href="#" class="group">Find</a> command and then will mark/unmark just those cards on which the targeted text is found.You can also mark/unmark cards by directly running the HyperTalk mark and unmark commands from the <a href="#" class="group">Message Box</a>. A very useful form of these commands is this: mark/unmark cards where expressionExpression can be any valid HyperTalk expression (see the manual for details). Here are some examples: mark cards where field "year" > 1980 mark cards where "linguistics" is not in field "keywords"</text> </content> <name>Marking and Unmarking Cards</name> <script></script> </card> card_6485.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>6485</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Searching</text> </content> <content> <layer>background</layer> <id>2</id> <text>o search for text in the bibliography cards, click on the Find button, choose Find on the Go menu, or press Command-F. You can specify how to search (Normal, Whole, Word(s), Chars, String) and where to search (anywhere or in a specified field).To find the next card which contains the search string, click on the Next button or press Command-G. If the search string is found in either of the pop-up fields User Fields or Annotation, the field will be opened on the screen.Note that the Next button (or Command-G) will not find more than one instance of the search string on the same card. To do this, just press Return repeatedly. This will execute the Find command as it is displayed in the <a href="#" class="group">Message Box</a>. However, this method will not display the pop-up fields if the search string is found in them.You can also use HyperCards's built-in Find command by typing the Find command directly into the <a href="#" class="group">Message Box</a>.If you try to search for a string that contains a double-quote character ("), HyperCard will report an error. To search for a string containing a double quote, replace the quote in the search string with: "&quote&" (including the " marks!). For instance to search for the word beitr\"{a}ge, type it into the Find dialog box as beitr\"&quote&"{a}ge. (This looks like an ill-formed string, but the Find command will supply quotes around the whole string, thus making it well-formed.)</text> </content> <name>Searching</name> <script></script> </card> card_6185.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>6185</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Sorting</text> </content> <content> <layer>background</layer> <id>2</id> <text>o sort the cards in the stack, use the Sort command on the Commands menu. You can choose to sort the cards on any significant field such as Key, <a href="#" class="group">Entry Type</a>, Author, Title, Year, Journal, and Publisher (fields such as Pages and Volume do not permit sorting). Note however that a given field may not occur on every card; for example, the Journal field occurs only on Article cards. If you sort the stack on the Journal field, then HyperCard will place all cards without that field first in the stack.If you are using a non-English version of HyperCard, click the button ΓÇ£Fix sort orderΓÇ¥ on the <a href="#" class="group">Preferences</a> card. You only need to do this once for a stack.You can achieve the effect of sorting on a primary and secondary field simply by sorting on those fields successively in reverse order. For example, if you want the stack sorted by author but cards with the same author to be subsorted by date, then first sort on the Year field and then sort again on the Author field.</text> </content> <name>Sorting</name> <script></script> </card> card_12250.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>12250</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Index Window</text> </content> <content> <layer>background</layer> <id>2</id> <text>he Index command on the Commands menu builds a list of <a href="#" class="group">entry key</a>s of the cards in the stack and places them in a pop-up window. You can build an index of either all cards or just the cards that currently are marked (see help card on <a href="#" class="group">Marking Card</a>s). Double-clicking on an <a href="#" class="group">entry key</a> listed in the Index window will take you to its card. You can scroll, move and zoom the index window in the usual way. You can also move the selection bar in the index window by holding down the option key and pressing the up or down arrow keys. Pressing option-Return or option-Enter has the same effect as double-clicking. You can reorder the list by holding down the option key and dragging an item to a new location. A special feature is available from the title card of the stack: if you hold down the option key and type a letter, the Index window will select the first matching item. (This feature may not work properly with non-English versions of HyperCard.)Note the following:ΓÇó If the <a href="#" class="group">entry key</a> of a card is empty, then that card will not be listed in the Index window.ΓÇó The Index window is not automatically updated when you edit an <a href="#" class="group">entry key</a>, add or delete cards, or mark or unmark cards. To update the Index, just execute the Index command again.</text> </content> <name>Index Window</name> <script></script> </card> card_8195.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>8195</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Abbreviations</text> </content> <content> <layer>background</layer> <id>2</id> <text>n abbreviation can be used in a field to stand for a longer piece of information. They are indicated with a dot (period) before them; e.g. the abbreviation .SIL stands for the organization name "Summer Institute of Linguistics". An abbreviation ΓÇ£is a string of characters that starts with a letter and does not contain a space or any of the following ten characters:ΓÇ¥ " # % ' ( ) , = { }Abbreviations can be used in fields for which <a href="#" class="group">authority list</a>s are maintained; these are: Author, Journal, Series, Type, Publisher, Organization, Institution, School, and Keywords. An abbreviation entry in an <a href="#" class="group">authority list</a> is a single line consisting of the abbreviation followed by an equals sign followed by the meaning of the abbreviation with delimiters around it (either quotes or braces). For example:.SIL="Summer Institute of Linguistics"Note: HyperBibTeX does NOT support concatenated abbreviations (introduced in BibTeX version 0.99b).You can choose whether or not abbreviations are expanded when cards are <a href="#" class="group">export</a>ed to a BibTeX file by clicking the appropriate box on the <a href="#" class="group">Preferences</a> card. If you do not choose to expand abbreviations, then all the abbreviations in the <a href="#" class="group">authority list</a>s will be exported as BibTeX @STRING definitions.You can also use abbreviations in fields which have no authority list. They will properly be exported as abbreviations, but of course cannot be expanded into their intended definitions.</text> </content> <name>Abbreviations</name> <script></script> </card> card_5990.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>5990</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Cross-references</text> </content> <content> <layer>background</layer> <id>2</id> <text>he three <a href="#" class="group">entry type</a>s InBook, InCollection, and InProceedings support the cross-referencing feature introduced in BibTeX version 0.99b. This permits you to have, say, two or more InProceedings entries that all point to the same Proceedings entry, thereby eliminating repeated information.For these three <a href="#" class="group">entry type</a>s, you can also make a card for the Book (for InBook and InCollection) or Proceedings (for InProceedings) item in which the excerpt is found. Enter the <a href="#" class="group">entry key</a> of the Book or Proceedings in the Book/Collection/ Proceedings CrossRef Key field. IMPORTANT: if the card key of the Book or Proceedings entry contains both the <a href="#" class="group">entry key</a> and a <a href="#" class="group">Key field</a> separated by an exclamation point, enter only the entry key (the part before the !) in the CrossRef Key field. (See also the Help card <a href="#" class="group">Entry Key versus Key Field</a>.) To jump to the Book or Proceedings entry, hold down the Command key and click on the CrossRef Key field.When cards of these three <a href="#" class="group">entry type</a>s are <a href="#" class="group">export</a>ed, the Book/ Collection/Proceedings CrossRef Key field is exported as a BibTeX CROSSREF field. Note that for the BibTeX program to be able to resolve cross-references, entries using the CROSSREF field must occur in the .BIB file before the cross-referenced entries. To ensure this order of entries when you <a href="#" class="group">export</a> cards to a .BIB file, go to the <a href="#" class="group">Preferences</a> card (choose Preferences on the Commands menu) and check the box ΓÇ£Export IN* entries first.ΓÇ¥Some BibTeX styles expect cross-referenced Book or Proceedings entries to include a BOOKTITLE field that is identical to the TITLE field. If BibTeX complains that your Book or Proceedings entries lack a BOOKTITLE field, then go to the <a href="#" class="group">Preferences</a> card of the stack, check the box ΓÇ£Include BookTitle field when exportingΓÇ¥, and <a href="#" class="group">export</a> the cards again. Otherwise, leave this box unchecked.If you do not want to make a separate cross-referenced entry (perhaps because only one entry references it), you can alternatively directly enter the appropriate BibTeX fields in the pop-up <a href="#" class="group">User Fields</a> (click the User Fields button). When you create an InBook, InCollection, or InProceedings entry, all the valid BibTeX fields will be placed in User Fields. (Tip to hackers: you can change the default set of user fields by editing three hidden card fields on the Preferences card, named InBookUserFields, InCollectionUserFields, and InProceedingsUserFields.)If you <a href="#" class="group">import</a> a BibTeX database file that uses cross-references, HyperBibTeX will create the proper entry cards and you are home free. However, if you <a href="#" class="group">import</a> InBook, InCollection, or InProceedings entries that don't use cross-references (that is, each entry includes fields for the Book or Proceedings in which the excerpt is located), then the fields for the corresponding Book/Collection/ Proceedings entry are placed in <a href="#" class="group">User Fields</a>.Note: Presently only three <a href="#" class="group">entry type</a>s permit cross- references: InBook, InCollection, and InProceedings. Is there any good reason why other entry types need a cross-reference field?</text> </content> <name>Cross-references</name> <script></script> </card> card_11087.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>11087</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>User-defined Fields</text> </content> <content> <layer>background</layer> <id>2</id> <text>he User Fields button brings up a scrolling field where the user can directly type user-defined fields in full BibTeX format. For example:TRANSLATOR = "T. Lator",ORIGINALTITLE = "Merkwaardige titel"No integrity checking of any kind is done on the contents of this field, so it is entirely up to the user to correctly follow BibTeX syntax. Note that each field should end with a comma, as BibTeX requires. Do not use a field name that is identical to any other valid BibTeX field name (but see below on the InBook, InCollection, and InProceedings entry types).The names of all user-defined fields in the entire stack should be listed in the box provided on the <a href="#" class="group">Preferences</a> card. For the entries above, the user-defined field names box should contain:TRANSLATORORIGINALTITLEwith one field name per line, each line ending with a Return. These field names are only used when <a href="#" class="group">import</a>ing entries from a .BIB file. Any extraneous fields used in a .BIB file whose names are not listed on the <a href="#" class="group">Preferences</a> card will be ignored, i.e. not imported. The <a href="#" class="group">entry type</a>s InBook, InCollection, and InProceedings have a slightly different behavior with respect to User Fields. For these entry types, you can put in User Fields standard BibTeX fields for the Book or Proceedings which contains the In... entry; for instance, BOOKTITLE, PUBLISHER, etc (see the <a href="#" class="group">Cross-reference</a>s help card). Provided that these are valid BibTeX field names for that <a href="#" class="group">entry type</a>, they do not have to be listed on the <a href="#" class="group">Preferences</a> card; they will automatically be <a href="#" class="group">export</a>ed and <a href="#" class="group">import</a>ed correctly.</text> </content> <name>User-defined Fields</name> <script></script> </card> card_2190.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>2190</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Entry Key versus Key Field</text> </content> <content> <layer>background</layer> <id>2</id> <text>ibTeX distinguishes between an entry key (used in the \cite command) and a Key field (used for alphabetizing an entry with no author/editor field). For example, look at this BibTeX entry:@PROCEEDINGS(COLING88,KEY = "Association for Computational Linguistics",TITLE = "...",ORGANIZATION = ACL }COLING88 is the entry key and "Association for Computational Linguistics" is the contents of the KEY field.HyperBibTeX does not have separate fields for entry key and Key field; they are both stored in the card key field. If you need a Key field, put it after the entry key separated by an exclamation point (!); for example, this is a legal card key field:COLING88!Association for Computational LinguisticsRemember that BibTeX will use a Key field for sorting only if the author/editor field is empty. When HyperBibTeX <a href="#" class="group">export</a>s an card that has an empty author/editor field, it will make a Key field in the exported entry (as in the BibTeX entry above). When HyperBibTeX <a href="#" class="group">import</a>s an entry with a Key field, it will contruct a card key using the ! separator.</text> </content> <name>Entry Key versus Key Field</name> <script></script> </card> card_12975.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>12975</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Handling accented characters</text> </content> <content> <layer>background</layer> <id>2</id> <text>eX requires an accented character such as ├⌐ to be encoded as {\'e} (unless you are using an eight-bit version of TeX that can handle accented characters). HyperBibTeX permits Macintosh accented characters to be used in the fields of the stack. When cards are <a href="#" class="group">export</a>ed, the accented characters are converted to to TeX macros. Conversely, when a .BIB file is <a href="#" class="group">import</a>ed, TeX macros are converted to their Mac equivalents. This behavior is optional and is controlled by a check box on the <a href="#" class="group">Preferences</a> card. Also on the Preferences card is a field containing a list of pairs of Mac accented characters and TeX macros, separated by a comma; for example: ├⌐,{\'e} ├╝,{\"u}If necessary, you can add more pairs to this list; but note that HyperBibTeX is limited to Geneva font. You can speed up exporting and importing by deleting pairs in the accents table that you do not need. If you do not want to use the character conversion feature at all, then be sure to uncheck the box "Convert accents".Note that LaTeX permits accented characters to be written as \'{e}, but BibTeX requires them to be written as either {\'e} or {\'{e}} in order to ensure correct sorting. If you are importing a .BIB file that uses these variants, you can add entries to the accents table to handle them; for example: ├⌐,{\'e} ├⌐,{\'{e}} ├⌐,\'{e}When you export, only the first entry for ├⌐ will be used, so no harm is done by retaining the other entries for ├⌐ in the list; but exporting will run a bit faster if you delete these extra entries.</text> </content> <name>Handling accented characters</name> <script></script> </card> card_5811.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>5811</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Entering Data</text> </content> <content> <layer>background</layer> <id>2</id> <text>o move from one field to another on a card, use the Tab key (or Return and Enter keys in nonscrolling fields) or click in a field.Field whose names are in boldface are required by BibTeX; other fields are optional (and some are extraneous).Use the general BibTeX conventions for entering data (opening and closing ``quote'' marks, -- is an en dash between page numbers, braces to prevent unwanted case conversion, etc.). See the LaTeX manual for details. Note that the ` (backquote) key will insert a ` (used by TeX as an opening quote mark). To do the Go Recent command, use Γîÿ~ or Esc. See also the help card on <a href="#" class="group">handling accented characters</a>.Enter new data in a field either by typing it in or for certain fields using special field entry buttons.New data typed into certain fields are verified against the <a href="#" class="group">authority list</a>s: Author/Editor, Journal, Series, Publisher, Organization, School, and Keywords. If you enter data in one of these fields that are not found in the appropriate authority list, a dialog box will appear that gives you opportunity to correct your entry or update the list, either by adding the entry to the list or by manually editing the list. The <a href="#" class="group">Preferences</a> card provides a button to turn verification on/off.These same fields also have field name buttons that bring up a dialog box with the appropriate <a href="#" class="group">authority list</a>. In the case of the Author/Editor and Keywords dialogs, you can make multiple selections at once by using either the shift key (for contiguous selection) or the command key (for noncontiguous selection). You can also use the arrow keys to move around in the list. If the list is alphabetical, typing letters will select the line that matches.If the insertion point is in one of the fields that has an authority list button, pressing ΓîÿReturn will have the same effect as clicking on the button.The Year and Month fields also have entry buttons. Click and hold to get a pop-up list of years and months. (The year and month lists can be customized by the user in the stack script.)Certain <a href="#" class="group">entry type</a>s can have either an author or editor (Book, InBook, and TechReport). To toggle the Author/Editor field name, click on the Role button.To see or edit the Annotation pop-up field, click the Annotation button. Click it again to hide it.To see or edit the pop-up field for <a href="#" class="group">user-defined fields</a>, click the User Fields button. Click it again to hide it.New Keywords can be added by command-clicking on a word in the Title field.</text> </content> <name>Entering Data</name> <script></script> </card> card_5625.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>5625</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Changing the Entry Type</text> </content> <content> <layer>background</layer> <id>2</id> <text>se the Change menu to change the <a href="#" class="group">entry type</a> of an existing card. For instance, suppose you enter all the information for a Book card and then realize that it should be a Proceedings type; just choose To Proceedings from the Change menu. Some fields will be copied into the Note field of the new Proceedings card. Use Cut and Copy Text to move the data into the proper fields.</text> </content> <name>Changing the Entry Type</name> <script></script> </card> card_8184.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>8184</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Setting Preferences</text> </content> <content> <layer>background</layer> <id>2</id> <text>o set various user preferences, choose the Preferences command on the Commands menu. Use <a href="#" class="group">balloon help</a> for information on the fields and buttons on the Preferences card.Number of years in Years button:Enter a number to set the number of years that you want shown in the Years button list.Style of name in Month button:Click the Short button to use three-letter abbreviations in the Month button (for example, .Jan).Click the Long button to use full-length names in the Month button (for example, January).Verify data entryCheck this box if you want new data typed into fields to be verified against the <a href="#" class="group">authority list</a>s. <a href="#" class="group">Entry key</a>s will also be checked.<a href="#" class="group">User-defined fields</a>:Enter a list of all names of user-defined fields used in this stack or in a .BIB file to be <a href="#" class="group">import</a>ed. These fields are accessed by the User Fields button. There should be one field name per line.BibTeX file name:Enter a file name to use as the default BibTeX (.BIB) file when <a href="#" class="group">exporting</a> cards.Stack ΓÇ£AboutΓÇ¥ button:Enter a description of this bibliography stack. It will be displayed when you click on the About button next to the stack name on the title card.Accents table:Enter a list of all <a href="#" class="group">accented characters</a> you intend to use in this stack. Each line should contain a Mac accented character and a TeX macro, separated by a comma. Edit this field with care!Fix sort orderClick this button to ensure that the Utility cards (i.e. the authority list cards and the preferences card) will be placed last in the stack when the stack is sorted. You normally only need to do this if you are using a non-English version of HyperCard (though it would not do any harm in any case). You only need to use this button once for each stack.The following options are relevant to <a href="#" class="group">exporting</a>.Convert accents (also on <a href="#" class="group">import</a>)Check this box if you want to convert Macintosh <a href="#" class="group">accented characters</a> (such as ├⌐) to TeX macros (such as {\'e}) when <a href="#" class="group">exporting</a>, and the reverse when <a href="#" class="group">importing</a>. The pairs in the Accents Table field will be used.Expand <a href="#" class="group">abbreviations</a>Check this box if you want abbreviations in fields to be replaced by their full equivalents when exporting cards to a BibTeX file. Otherwise abbreviations (and their definitions) will be exported.Include BookTitle fieldCheck this box if you are using the <a href="#" class="group">CrossRef</a> field and want a BookTitle field to be included with each <a href="#" class="group">cross-reference</a>d Book or Proceedings entry when it is exported.Export IN* entries first:Check this box if you want to <a href="#" class="group">export</a> InBook, InCollection, and InProceedings entries before all other entries. This is necessary only if the In* entries contain <a href="#" class="group">CrossRef</a> fields.Field delimitersClick the "..." button to use quotes as field delimiters when exporting. Note that if a field contains a quote mark (such as {\"u}), the field will be delimited by braces even though the default is quotes.Click the {...} button to use braces as field delimiters when exporting.</text> </content> <name>Setting Preferences</name> <script></script> </card> card_5349.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>5349</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Making New Cards</text> </content> <content> <layer>background</layer> <id>2</id> <text>se the New menu to make a new card.ΓîÿN (New Card on the Edit menu) will make a new card of the same <a href="#" class="group">entry type</a> as the current card.You can also use Copy Card and Paste Card on the Edit menu to duplicate an existing card.</text> </content> <name>Making New Cards</name> <script></script> </card> card_9209.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>9209</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Making a New Stack</text> </content> <content> <layer>background</layer> <id>2</id> <text>o make a new stack, use the blank stack that is supplied with HyperBibTeX.Otherwise, to make a new stack from an existing (non-blank) stack:(1) Open an existing HyperBibTeX stack.(2) Choose the command Save a Copy... on the File menu and make a copy of the current stack with the name you desire for the new stack.(3) Open the new stack.(4) Choose <a href="#" class="group">Mark Card</a>s on the Commands menu and mark all cards.(5) Choose Delete <a href="#" class="group">Marked Card</a>s on the Commands menu.(6) Edit the <a href="#" class="group">Preferences</a> card and the <a href="#" class="group">Authority List</a>s cards.</text> </content> <name>Making a New Stack</name> <script></script> </card> card_4979.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>4979</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Navigation</text> </content> <content> <layer>background</layer> <id>2</id> <text>rrow buttons on each card go to previous or next card.Option- or Γîÿ-arrow buttons go previous/next <a href="#" class="group">marked card</a>.Option-left/right arrow keys go previous/next card (including <a href="#" class="group">Authority List</a> cards).Γîÿ-left/right arrow keys go previous/next <a href="#" class="group">marked card</a>.Γîÿ2/3 (Prev and Next on Go menu) and PageUp/PageDown keys go previous/next card (including <a href="#" class="group">Authority List</a> cards).Γîÿ1 (First on Go menu) and Home keys go first card.Γîÿ4 (Last on Go menu) and End keys go last bib card (not last card in stack).Esc, Γîÿ~ (Back on Go menu), and down arrow go back.ΓîÿJ (Navigator on Go menu) shows/hides Navigator palette.ΓîÿH (Home on Go menu) goes to Home stack.Γîÿ? (Help on Go menu) goes to either this stack or the Hypercard Help stack.The <a href="#" class="group">Index Window</a> permits you to jump to any card listed there.</text> </content> <name>Navigation</name> <script></script> </card> card_10234.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>10234</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>2</id> <text>ere are the BibTeX definitions of the thirteen entry types.Note: The terms Required, Optional, and Ignored refer to the way they are treated by BibTeX, not necessarily HyperBibTeX. For instance, BibTeX will ignore the Location and Keywords fields in a .BIB database file, but HyperBibTeX will correctly <a href="#" class="group">export</a> and <a href="#" class="group">import</a> these fields.Note: Key in the descriptions below refers to the entry key used in BibTeX's \cite command. See the Help card on <a href="#" class="group">Entry Key versus Key Field</a> for details.Article Required: key, author, title, journal, year Optional: volume, number, month, pages, note Ignored: location, keywords, annoteBook Required: key, author or editor, title, year, publisher, Optional: edition, volume, month, series, number, address, note Ignored: pages, ISBN, location, keywords, annoteBooklet Required: key, title Optional: author, year, month, address, howpublished, note Ignored: pages, location, keywords, annoteConference Not supported. Same as InProceedings.InBook Required: key, author or editor, title, year, chapter and/or pages, publisher Optional: edition, volume or number, series, chapter, type, month, note, crossref Ignored: ISBN, pages, location, keywords, annote InCollection Required: key, author, title, booktitle, year, publisher Optional: edition, volume or number, series, chapter, type, month, pages, address, note, crossref Ignored: ISBN, location, keywords, annoteInProceedings Required: key, author, title, booktitle, year Optional: edition, volume or number, series, chapter, pages, month, address, publisher, organization, note, crossref Ignored: ISBN, location, keywords, annote Manual Required: key, title Optional: author, year, month, edition, address, organization, note Ignored: pages, location, keywords, annoteMastersThesis Required: key, author, title, year, school Optional: month, type, address, note Ignored: pages, location, keywords, annoteMisc Required: key Optional: author, title, year, month, howpublished, note Ignored: pages, location, keywords, annotePhDThesis Required: key, author, title, year, school Optional: month, type, address, note Ignored: pages, location, keywords, annoteProceedings Required: key, title, year Optional: editor, month, volume, series, number, address, organization, publisher, note Ignored: pages, ISBN, location, keywords, annoteTechReport Required: key, author or editor, title, year, institution Optional: month, type, number, address, note Ignored: pages, location, keywords, annoteUnpublished Required: key, author, title, note Optional: year, month Ignored: pages, location, keywords, annote</text> </content> <content> <layer>background</layer> <id>1</id> <text>Definitions of Entry Types</text> </content> <name>Definitions of Entry Types</name> <script></script> </card> card_9968.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>9968</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Using Balloon Help</text> </content> <content> <layer>background</layer> <id>2</id> <text>To use Balloon Help, choose "Show Balloons" on the system 7 Help menu (a question mark in a balloon) . Now move the mouse pointer over various buttons and fields. (There is no Balloon Help for menu items.) To stop using Balloon Help, choose "Hide Balloons" from the Help menu.Balloon Help is not available under system 6.</text> </content> <name>Using Balloon Help</name> <script></script> </card> card_2440.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>2440</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Bugs in HyperBibTeX</text> </content> <content> <layer>background</layer> <id>2</id> <text>yperBibTeX version 0.9.5 (0.9.5d, 0.9.5e, and 0.9.5f) had two serious bugs: ΓÇó the <a href="#" class="group">Export</a> command dropped certain non-BibTeX fields ΓÇó the <a href="#" class="group">Import</a> command didn't properly import some <a href="#" class="group">user-defined fields</a>These bugs have been fixed in version 0.9.6. Do not continue to use version 0.9.5! See the Help card on <a href="#" class="group">Upgrading</a> a stack to a new version of HyperBibTeX.One user could not use HyperBibTeX with the French version of HyperCard Player. I have not been able to verify this, since I don't have access to French HC Player. If anyone has problems using HyperBibTeX with non-English versions of HyperCard, please report them to me.</text> </content> <name>Bugs in HyperBibTeX</name> <script></script> </card> card_11475.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>11475</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>Installing HyperBibTeX</text> </content> <content> <layer>background</layer> <id>2</id> <text>HyperBibTeX requires HyperCard 2.0 or higher. Version 2.1 is recommended because it offers better error handling. HyperBibTeX will run under either system 6 or system 7, but Balloon Help is available only under system 7.HyperBibTeX uses two auxiliary stacks: HyperBibTeX Utils and HyperBibTeX Help. You should have only one copy each of these stacks on your system. Place them in a folder where HyperCard can find them; that is, put them in a folder listed on the Stacks Search Paths card of your Home stack.Bibliography stacks created with HyperBibTeX can be located anywhere on your disk. You can make buttons in your Home stack that link to your bibliography stacks.</text> </content> <name>Installing HyperBibTeX</name> <script></script> </card> card_4363.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>4363</id> <filler1>0</filler1> <cantDelete> <false /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <false /> </dontSearch> <owner>4305</owner> <marked><true /></marked> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <content> <layer>background</layer> <id>1</id> <text>About HyperBibTeX</text> </content> <content> <layer>background</layer> <id>2</id> <text>his stack maintains a database of bibliographic entries in a structure that is compatible with BibTeX. It has facilities for: ΓÇó entering and editing bibliographic entries using BibTeX's <a href="#" class="group">entry types</a> (Book, Article, Proceedings, etc.), ΓÇó verifying data against a set of <a href="#" class="group">authority list</a>s, ΓÇó <a href="#" class="group">searching</a> the database, ΓÇó <a href="#" class="group">marking card</a>s individually or with the search function, ΓÇó <a href="#" class="group">sorting</a> cards on various fields, ΓÇó <a href="#" class="group">export</a>ing cards to a BibTeX file, ΓÇó <a href="#" class="group">import</a>ing entries from a BibTeX file.Familiarity with Tex and BibTeX is assumed. For a description of BibTeX, see "LaTeX, A Document Preparation System," by Leslie Lamport, Addison-Wesley Publishing Company, 1986, Appendix B. A revised version of BibTeX (0.99b) is described in the document ΓÇ£BibTeXingΓÇ¥, by Oren Patashnik.BibTeX features unsupported by HyperBibTeX (see also the Help card on <a href="#" class="group">import</a>ing): ΓÇó concatenated <a href="#" class="group">abbreviation</a>s (introduced in BibTeX version 0.99b); ΓÇó parentheses as outermost delimiters of an entry (recognizes only braces as entry delimiters, but does support both braces and double-quotes as field delimiters).HyperBibTeX is copyrighted by the Summer Institute of Linguistics, Dallas, TX. It may be freely distributed provided that: (1) all the files in the original release are included in unmodified form and (2) no charge is added except for media or postage. Please send correspondence about HyperBibTeX to:Evan AntworthAcademic Computing Dept.Summer Institute of Linguistics7500 W. Camp Wisdom RoadDallas, TX 75236U.S.A.phone: 214-709-3346, -2418fax: 214-709-3380Internet e-mail: Evan.Antworth@sil.org</text> </content> <name>About HyperBibTeX</name> <script></script> </card> card_2941.xml <?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE card PUBLIC "-//Apple, Inc.//DTD card V 2.0//EN" "" > <card> <id>2941</id> <filler1>0</filler1> <bitmap>BMAP_4019.pbm</bitmap> <cantDelete> <true /> </cantDelete> <showPict> <true /> </showPict> <dontSearch> <true /> </dontSearch> <owner>2726</owner> <link rel="stylesheet" type="text/css" href="stylesheet_3253.css" /> <part> <id>1</id> <type>field</type> <visible> <true /> </visible> <dontWrap> <true /> </dontWrap> <dontSearch> <true /> </dontSearch> <sharedText> <false /> </sharedText> <fixedLineHeight> <true /> </fixedLineHeight> <autoTab> <false /> </autoTab> <lockText> <true /> </lockText> <rect> <left>133</left> <top>60</top> <right>342</right> <bottom>261</bottom> </rect> <style>scrolling</style> <autoSelect> <false /> </autoSelect> <showLines> <false /> </showLines> <wideMargins> <true /> </wideMargins> <multipleLines> <false /> </multipleLines> <reservedFamily> 0 </reservedFamily> <titleWidth>0</titleWidth> <icon>0</icon> <textAlign>left</textAlign> Geneva <textSize>12</textSize> <textStyle>plain</textStyle> <textHeight>16</textHeight> <name>Topic List</name> <script>on mouseDownif the optionKey is down thenmakeTopicList -- rebuild listexit mouseDownend ifgoTopicend mouseDownon mouseEnterballoon "Click on a topic."end mouseEnteron makeTopicListput empty into meset cursor to watchrepeat with x = 1 to (number of cds in bg "Help Cards")put truncateName(short name of cd x of bg "Help Cards")&return ┬¼into line x of meend repeatdelete last char of meend makeTopicList</script> </part> <part> <id>3</id> <type>button</type> <visible> <true /> </visible> <reserved5> 0 </reserved5> <reserved4> 0 </reserved4> <reserved3> 0 </reserved3> <reserved2> 0 </reserved2> <reserved1> 0 </reserved1> <enabled> <true /> </enabled> <rect> <left>395</left> <top>188</top> <right>438</right> <bottom>218</bottom> </rect> <style>transparent</style> <showName> <false /> </showName> <highlight> <false /> </highlight> <autoHighlight> <true /> </autoHighlight> <sharedHighlight> <true /> </sharedHighlight> <family>0</family> <titleWidth>0</titleWidth> <icon>25002</icon> <textAlign>center</textAlign> Chicago <textSize>12</textSize> <textStyle>plain</textStyle> <name>New Button</name> <script>on mouseUpanswer "Find a topic of interest in the scrolling field on this"┬¼&&"card and click on it. This will take you to a Help Topic card."┬¼&&"Clicking on text with a grey underline takes you to a related"┬¼&&"topic card. Click on the Print button to print a copy of the"┬¼&&"Help Topics."end mouseUpon mouseEnterballoon "Click for help with this stack."end mouseEnter</script> </part> <part> <id>5</id> <type>field</type> <visible> <false /> </visible> <dontWrap> <true /> </dontWrap> <dontSearch> <true /> </dontSearch> <sharedText> <false /> </sharedText> <fixedLineHeight> <false /> </fixedLineHeight> <autoTab> <false /> </autoTab> <lockText> <true /> </lockText> <rect> <left>29</left> <top>246</top> <right>114</right> <bottom>263</bottom> </rect> <style>rectangle</style> <autoSelect> <false /> </autoSelect> <showLines> <false /> </showLines> <wideMargins> <false /> </wideMargins> <multipleLines> <false /> </multipleLines> <reservedFamily> 0 </reservedFamily> <titleWidth>0</titleWidth> <icon>0</icon> <textAlign>left</textAlign> Geneva <textSize>12</textSize> <textStyle>plain</textStyle> <textHeight>16</textHeight> <name>Help Stack Version</name> <script></script> </part> <part> <id>8</id> <type>button</type> <visible> <true /> </visible> <reserved5> 0 </reserved5> <reserved4> 0 </reserved4> <reserved3> 0 </reserved3> <reserved2> 0 </reserved2> <reserved1> 0 </reserved1> <enabled> <true /> </enabled> <rect> <left>392</left> <top>233</top> <right>441</right> <bottom>258</bottom> </rect> <style>roundrect</style> <showName> <true /> </showName> <highlight> <false /> </highlight> <autoHighlight> <true /> </autoHighlight> <sharedHighlight> <true /> </sharedHighlight> <family>0</family> <titleWidth>0</titleWidth> <icon>0</icon> <textAlign>center</textAlign> Chicago <textSize>12</textSize> <textStyle>plain</textStyle> <name>Print</name> <script>on mouseUpanswer "Print 32 pages of Help Topics?"┬¼&return&"(Note that Help Topics longer than a page will be truncated!)"┬¼with "Cancel" or "OK"if it is "Cancel" then exit mouseUpopen report printing with template "Title Card"print cd 1close printingmark all cdsunmark cd 1open report printing with template "Help Topics"print marked cdsclose printingend mouseUpon mouseEnterballoon "Click to print the Help Topics."end mouseEnter</script> </part> <part> <id>9</id> <type>field</type> <visible> <true /> </visible> <dontWrap> <false /> </dontWrap> <dontSearch> <false /> </dontSearch> <sharedText> <false /> </sharedText> <fixedLineHeight> <false /> </fixedLineHeight> <autoTab> <false /> </autoTab> <lockText> <true /> </lockText> <rect> <left>133</left> <top>22</top> <right>326</right> <bottom>40</bottom> </rect> <style>transparent</style> <autoSelect> <false /> </autoSelect> <showLines> <false /> </showLines> <wideMargins> <false /> </wideMargins> <multipleLines> <false /> </multipleLines> <reservedFamily> 0 </reservedFamily> <titleWidth>0</titleWidth> <icon>0</icon> <textAlign>center</textAlign> Chicago <textSize>12</textSize> <textStyle>plain</textStyle> <textHeight>16</textHeight> <name>Stack Title</name> <script></script> </part> <part> <id>4</id> <type>button</type> <visible> <true /> </visible> <reserved5> 0 </reserved5> <reserved4> 0 </reserved4> <reserved3> 0 </reserved3> <reserved2> 0 </reserved2> <reserved1> 0 </reserved1> <enabled> <true /> </enabled> <rect> <left>299</left> <top>8</top> <right>339</right> <bottom>40</bottom> </rect> <style>transparent</style> <showName> <false /> </showName> <highlight> <false /> </highlight> <autoHighlight> <true /> </autoHighlight> <sharedHighlight> <true /> </sharedHighlight> <family>0</family> <titleWidth>0</titleWidth> <icon>19678</icon> <textAlign>center</textAlign> Chicago <textSize>12</textSize> <textStyle>plain</textStyle> <name>About HyperBibTeX</name> <script>on mouseUpanswer "HyperBibTeX Stack version 0.9.8, 27-Sep-93"┬¼&return&"Copyright ┬⌐1993 Summer Institute of Linguistics, Inc."┬¼&&"All Rights Reserved."┬¼&return&return&"Send correspondence to Evan.Antworth@sil.org"end mouseUpon mouseEnterballoon "Click for information about HyperBibTeX Help."end mouseEnter</script> </part> <content> <layer>card</layer> <id>5</id> <text>0.9.5e</text> </content> <content> <layer>card</layer> <id>9</id> <text>HyperBibTeX Help Topics</text> </content> <content> <layer>card</layer> <id>1</id> <text>About HyperBibTeXInstalling HyperBibTeXBugs in HyperBibTeXUsing Balloon HelpDefinitions of Entry TypesNavigationMaking a New StackMaking New CardsSetting PreferencesChanging the Entry TypeEntering DataHandling accented charactersEntry Key versus Key FieldUser-defined FieldsCross-referencesAbbreviationsIndex WindowSortingSearchingMarking and Unmarking CardsChecking KeysFinding Duplicate CardsAuthority ListsVerifying Field ContentsExportingImportingUpgrading to a new version oPrinting CardsCommand KeysFunction KeysUsing the Message Box</text> </content> <name>Topic List</name> <script>on openCardglobal topicNumberif topicNumber is not empty thenselectWholeLine topicNumber, the name of cd fld "Topic List"end ifend openCard</script> </card>